Personal digital assistant module having a broadcast pointer device

ABSTRACT

A personal digital assistant module with a local CPU, (central processing unit) memory, and I/O (input/output) interface has a host interface comprising a bus connected to the local CPU and a connector at a surface of the personal digital assistant for interfacing to a bus connector of a host general-purpose computer, providing direct bus communication between the personal digital assistant and the host general-purpose computer. In an embodiment, the personal digital assistant also stores a security code. The personal digital assistant according to the invention forms a host/satellite combination with a host computer having a docking bay, wherein upon docking a docking protocol controls access by the host to memory of the personal digital assistant based on one or more passwords provided by a user to the host. In another embodiment the personal digital assistant also has an expansion port connected to the local CPU, and expansion peripheral devices may be connected and operated through the expansion port. Connectable devices may include input devices such as pointer devices, that may in some cases be stored in a compartment fashioned for the purpose in the personal digital assistant.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a continuation of application Ser. No. 08/310,944 filed Sep. 22,1994, now abandoned.

FIELD OF THE INVENTION

This invention is in the area of portable computers and pertains morespecifically to small portable computing devices known in the art aspersonal digital assistants.

BACKGROUND OF THE INVENTION

Personal Digital Assistant (PDA) units, as of the date of thisdisclosure, enjoy a position of hope in the computer marketplace. Somebelieve this approach, a small, relatively inexpensive, and eminentlyportable computer unit, having software specifically written for tasks auser might expect to perform while travelling, will provide eminentlyuseful and therefore salable computer products. Apple Computer, HewlettPackard, and several other well-known computer manufacturers have made aconsiderable investment at no small risk in such systems.

Given the new systems now introduced, and those coming, for what is nowknown about them, there are still a number of drawbacks and problems.For example:

1. The PDA systems introduced are relatively costly, with startingprices ranging from several hundred dollars to two thousand dollars andmore. At such prices, rivalling current pricing for desktop systems, thebuying public may react negatively. It is true that prices will fallwith increased manufacturing volume and competition, but the high endstart may well be rejected by potential users.

2. The systems being offered are still relatively bulky, considering thelimited range of tasks that may be accomplished. Most are certainly toobig to be conveniently carried in a breast pocket. The Newton,manufactured by Apple Corporation, weighs about a pound and isapproximately the size of a VHS video cassette.

3. A big drawback of the PDA systems being offered is the way theytransfer data between a user's desktop unit, or other host, and the PDA.Known communication is by modem, by infrared communication, and byserial connection. These all require manipulation by a user, modulationon one or both ends of the communication path, and the like, which canbe time-consuming, error-prone, and hardware extensive (expensive).Presently the Newton offers a modem and/or LED communication as anoption, adding to the overall cost.

4. In known PDAs, software is typically recorded in ROM, so updatingapplications can be difficult, and sometimes impossible. This will be aproblem because PDA users will not want the PDA to have the samecapabilities at all times. Typical users will be people who travel andwork while they travel. These users require different functions for atrip to Taiwan than for a trip to France, for example. What is needed isa quick and convenient means to update and substitute software.

5. Another difficulty is in the fact that the data files a usermanipulates while travelling are typically data files also resident in ahome unit, herein called a host unit, such as the user's office desktopmachine or notebook or other portable computer. It is very troublesometo have two or more sets of critical data, with differences that onemust remember to correct at an appropriate time. This can cause unendinggrief if files are not correctly updated. At best, current PDAs must usea relatively slow compressed bus to download and upgrade files.Typically this is done through a serial port, using a linkingapplication like Laplink™.

What is needed is a small and inexpensive PDA that has a range offeatures that eliminate the above-described risks and problems. This newunit needs to be smaller than those presently being introduced, such asabout credit-card size, or perhaps modeled on the PCMCIA type II or typeIII standard form factors. It should be inexpensive enough to producethat at least a minimum version could be sold in the roughly $100-$200range, so it will be a unit seen to be a relatively inexpensivenecessity. A PDA unit of this sort is the subject of the presentinvention, and is termed by the inventors a micro-PDA, or μPDA.

A very important feature of the μPDA in an aspect of the presentinvention is a direct parallel bus interface with a connector allowingthe unit to be docked by plugging it into a docking bay in a host unit.Moreover, when the μPDA is docked in the host, there needs to be a meansto effectively disable the CPU in the μPDA and to provide direct accessto both the μPDA software and data storage by the host CPU. This directaccess would provide immediate ability to communicate in the fastestavailable fashion between the μPDA and the host, and would alsofacilitate additional important features to be described below.

The μPDA also needs to have an optional compressed bus interface,including a connector separate from the host interface, so add-ondevices may be utilized, such as a FAX modem, cellular communication,printer, and so on.

An additional feature that could be optionally provided in anotheraspect of the invention is an interface at the host to allow a user toselect pre-arranged software mixes for loading to the μPDA. This featurecomprises a set of control routines operating in conjunction with thehost's display and input means, to allow the user to quickly selectapplications and perhaps data as well to be loaded to the μPDAsatellite, to configure the smaller, more portable unit for specificitineraries and purposes.

Another desirable feature is an ability to automatically update datafiles. In this aspect of the invention, with the μPDA docked, data onthe host, if carrying a later date and/or time stamp than the data onthe μPDA, would be automatically updated on the μPDA and vice-versa.When one returns from an excursion using the μPDA and docks thesatellite at the host, the host gains access, determines the location ofthe latest files, and accomplishes the update. This feature needs tohave some built-in user prompting to be most effective. It makes theμPDA a true satellite system.

SUMMARY OF THE INVENTION

In a preferred embodiment of the invention a personal digital assistantmodule is provided comprising an enclosure for enclosing and supportinginternal elements, a microcontroller within the enclosure for performingdigital operations to manage functions of the personal digital assistantmodule, and a memory means connected to the microcontroller by a memorybus structure for storing data and executable routines. There is a powersupply means within the enclosure for supplying power to functionalelements of the personal digital assistant module, a display meansoperable by the microcontroller and implemented on a surface of theenclosure, and input means connected to the microcontroller forproviding commands and data to the personal digital assistant module. Ahost interface means comprising a host interface bus structure, whichmay be configured as a PCMCIA bus interface, is connected to themicrocontroller and to a first portion of a host interface connector ata surface of the enclosure, and the host interface means is configuredto directly connect the microcontroller to a compatible bus structure ofa host computer.

In one embodiment the personal digital assistant module has an expansionbus interface comprising an expansion bus structure connected to themicrocontroller and to a first portion of an expansion bus connector forconnecting the microcontroller to a peripheral device. A wide variety ofperipheral devices are provided for use with the personal digitalassistant of the invention.

In another aspect, the personal digital assistant module also has anonvolatile storage device, such as an EEPROM connected to themicrocontroller and containing one or more codes unique to the personaldigital assistant, for uniquely identifying the personal digitalassistant to digital devices connected on the host interface.

In a preferred embodiment, the display and input means for the personaldigital assistant are configured as an overlaid touch screen and LCDdisplay on a surface of the outer case of the personal digitalassistant. A pointer device implemented as a thumbwheel in oneembodiment and as a pressure sensitive pad in another is provided aspart of the input capability.

In other embodiments the personal digital assistant module hasattachable pointer devices and other input devices. In some of thesealternative embodiments pointer devices may be stored in a compartmentin the personal digital assistant and deployed for use.

The personal digital assistant module forms a unique combination with ageneral-purpose computer host having the personal digital assistant as asatellite unit. The host in this instance has a docking bay especiallyconfigured to dock the personal digital assistant, making a direct busconnection between the local CPU of the personal digital assistant andthe CPU of the host. The host may be a desktop unit, a notebookcomputer, or a smaller portable like a palmtop computer. Thiscombination provides power and convenience not before available.

Many other digital devices are also provided according to variousaspects of the invention, such as modems, scanners, data acquisitionperipherals, cellular phones, and a software vending machine, and all ofthese devices may be appended to the personal digital assistant by theexpansion bus interface or, in many cases, by the host interface.

The personal digital assistant provided according to embodiments of thepresent invention is a unit more compact than conventional PDAs. Itrepresents a new dimension in computer application and applicability, ina form promising to be eminently usable by and useful to almosteveryone; and at a price easily affordable. It solves the communicationproblem intrinsic to personal digital assistants relative to larger andmore powerful computers, with a unit that fits into a user's breastpocket, and at a very low price.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is an isometric view of a μPDA according to an embodiment of thepresent invention.

FIG. 1B is a plan view of the μPDA of FIG. 1A.

FIG. 2 is a cross-sectional view of the μPDA of FIGS. 1A and 1B.

FIG. 3 is a block diagram of the μPDA of FIG. 1A and some peripheralelements.

FIG. 4 is a more detailed plan view of the μPDA of FIG. 1A showing inparticular an LCD display and touch screen user interface in an aspectof the present invention. FIG. 5 is an isometric view of a μPDA and ahost notebook computer in an aspect of the present invention, with theμPDA about to be docked in a docking bay of the notebook computer.

FIG. 6 is a block diagram of a μPDA docked in a docking bay of a hostcomputer according to an embodiment of the present invention.

FIG.7 is a logic flow diagram of the steps in docking a μPDA in a hostcomputer according to an embodiment of the present invention.

FIG. 8 is an isometric illustration of a μPDA software vending machinein an aspect of the present invention.

FIG. 9 is a top plan view of a μPDA enhanced user interface according toan embodiment of the present invention.

FIG. 10 is a top plan view of a μPDA with a microphone in an embodimentof the present invention.

FIG. 11 is an isometric drawing of a μPDA docked in a dedicated cellularor cordless telephone according to an embodiment of the presentinvention.

FIG. 12 is a plan view of a μPDA with a speaker and pager interfaceaccording to an embodiment of the present invention.

FIG. 13 is a plan view of a μPDA with an infrared communicationinterface according to an embodiment of the present invention.

FIG. 14 is a plan view of a μPDA with a scanner attachment according toan embodiment of the present invention.

FIG. 15 is a plan view of a μPDA with a fax-modem attached according toan embodiment of the present invention.

FIG. 16 is a plan view of a μPDA with a printer adapter interfaceaccording to an embodiment of the present invention.

FIG. 17 is an isometric drawing of a μPDA docked in a barcode readerproviding a data acquisition peripheral according to an embodiment ofthe present invention.

FIG. 18 is an isometric view of a μPDA with a solar charger according toan embodiment of the present invention.

FIG. 19 is a plan view of four μPDAs interfaced to a dedicated networkconsole providing inter-PDA communication according to an embodiment ofthe present invention.

FIG. 20 is an isometric view of a μPDA according to the inventionconnected by the expansion port to a standard-sized keyboard.

FIG. 21A is an isometric view of a notebook-type computer with aremovable pointer device stored in an on-board compartment according toan embodiment of the present invention.

FIG. 21B is an isometric view of the notebook-type computer of FIG. 21awith a mouse pointer device deployed for use, having a connecting cable.

FIG. 21C is an isometric view of a notebook-type computer with Acordless mouse device deployed for use.

FIG. 21D is an isometric view of a notebook-type computer with acord-connected trackball device deployed for use.

FIG. 21E is an isometric view of a notebook-type computer with acordless trackball device deployed for use.

FIG. 21F is an isometric view of a notebook-type computer with acord-connected combination mouse/trackball device deployed for use.

FIG. 21G is an isometric view of a notebook-type computer with acordless combination mouse/trackball device deployed for use.

FIG. 21H is an isometric view of a notebook-type computer with atrackball pointer mounted in a well according to an embodiment of thepresent invention.

FIG. 21I is an isometric view similar to FIG. 21H, showing the trackballpointer deployed for use away from the well.

FIG. 22 is a plan view of the removable pointer device of FIG. 21H and21I, and surrounding areas of the host.

FIG. 23 is a mostly diagrammatic representation of internal componentsof the removable pointer device of FIGS. 21H, 21I and 22.

FIG. 24 is a mostly diagrammatic representation of internal componentsof a removable pointer device according to an alternative embodiment ofthe present invention.

FIG. 25A is a plan view of a combined removable pointer device accordingto an alternative embodiment of the present invention.

FIG. 25B is a plan view of the pointer device of FIG. 25A, showing theopposite side.

FIG. 25C is an elevation view of a combined removable pointer deviceaccording to an alternative embodiment of the present invention.

FIG. 25D is a mostly diagrammatic representation of the internalcomponents of the combined removable pointer device of FIG. 25C.

FIG. 26A is a plan view of a polar-coordinate pointer device stored in acompartment in a host computer according to an alternative embodiment ofthe present invention.

FIG. 26B is a plan view of the polar-coordinate pointer device of FIG.26A, with the pointer device extended for use.

FIG. 26C is a graphic illustration of the geometry involved in thecalculation of the Cartesian of the polar-coordinate pointer device inFIG. 26B.

FIG. 27A is a plan view of a broadcast pointer system with a deployableelement and a storage compartment according to an alternative embodimentof the present invention.

FIG. 27B is a plan view of the broadcast pointer device of FIG. 27A withthe deployable element deployed.

FIG. 27C is a plan view of another broadcast pointer system with astylus-type deployable element.

FIG. 27D is an illustration of a waveform as received by antenna 1319from pointer 1321.

FIG. 28 is an isometric view of a keyboard having a removable pointerdevice according to a preferred embodiment of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1A is an isometric view of a μPDA 10 according to an embodiment ofthe present invention. In this embodiment the unit is modeled on thePCMCIA standard Type II form factor, having a height D1 of about 5 mm.Body 12 is described in further detail below, and has a female portion14 of a connector recessed at one end for engaging a mating male portionof the connector in a host computer, connecting the μPDA internalcircuitry directly with a host internal bus. The host unit may be anotebook computer having a docking bay for the μPDA. Docking bays may beprovided in desktop and other types of computers, and even in otherkinds of digital equipment, several examples of which are describedbelow.

Still referring to FIG. 1A, in this embodiment there is a combinationI/O interface 16 implemented on one side of the μPDA, comprising adisplay overlaid with a touch-sensitive planar structure providingsoftkey operation in conjunction with interactive control routinesoperable on the μPDA in a stand-alone mode.

Although not shown in FIG. 1A, there may also be guides implementedalong the sides of the case of the device for guiding the module in andout of a docking bay in a host computer unit. There may also be one ormore mechanical features facilitating engagement and disengagement ofthe module in a docking bay.

FIG. 1B is a top plan view of the μPDA of FIG. 1A showing a thumbwheel18 implemented in one corner of the μPDA. The thumbwheel in thisembodiment is an input device capable of providing input with bothamplitude and directional characteristics, and in some cases ratecharacteristics as well. The thumbwheel has many uses in combinationwith the μPDA and I/O interface 16. One such use is controlled scrollingof icons, characters, menus, and the like on the display of the device.The thumbwheel provides many of the functions of a pointer device.

In this embodiment of the μPDA a second external connector portion 20 isprovided. This connector portion is for engaging peripheral devices aspart of an expansion bus interface.

FIG. 2 is a simplified cross-sectional view of a means for constructinga μPDA according to the present invention in a Type II PCMCIA, or otherrelatively small package. ICs 34 are encapsulated in a conformalmaterial 36, and interconnection is accomplished by traces on a flexiblepolymer film 32 shown as overlaying the encapsulated structure. In thisstructure the ICs are not packaged in the conventional manner havingsolder leads for assembly to a printed circuit board. Rather,connections are made directly between the solder pads on the chip andthe traces on the Kapton film. Also there is no intention to relate ICsindicated by element No. 34 with specific functional lCs in a μPDA. Thiscross-section is illustrative of a method of construction only.

In this compact construction there may also be traces on the side offilm 32 away from the interconnections for the CPU and memory forconnection to other elements, such as display 25 and touch-sensitivescreen 27.

LCD display 25 is implemented on one side of the μPDA, andtouch-sensitive interface 27 is provided overlaying at least a portionof the LCD display. A metal casing 38, or other suitable material orcombinations of material, surrounds the internal components and conformsto Type II PCMCIA form factors. This simplified cross-sectionillustrates some of the principles of construction that can allow theneeded components to be inexpensively fitted into the small form factorneeded. In another embodiment the μPDA is implemented in the form factorof a type III (10 mm thick) PCMCIA unit, using relatively conventionaltechnology, such as PCB technology, rather than the encapsulatedconstruction described immediately above. Various other constructions,form factors, and combinations are possible, as well.

FIG. 3 is a simplified electrical block diagram of the μPDA of FIGS. 1A,1B and 2. A unique microcontroller 11 acts as the CPU of the μPDA in thestand-alone mode, that is, when the μPDA is not docked in a host unit.When the μPDA is docked in a host computer, microcontroller 11 acts as aslave unit, granting bus control to the CPU of the host. In docked mode,the CPU of the host thus gains control of the memory contents of theμPDA, subject in most cases to security procedures which are describedbelow. Thus the host computer can transfer data and software into andout of a docked μPDA memory. In other embodiments many other cooperativeoperating modes may be accomplished between the two CPUs and accessiblememory devices.

Memory 13 is preferably a nonvolatile device from 1 to 2 megabytes inthis embodiment, and both control routines for applications and datafiles are stored in this memory. Memory 13 may be flash memory, CMOSROM, CMOS RAM with battery, or a combination, with the software storedin ROM and the data in the flash memory. The memory device is interfacedto microcontroller 11 via a dedicated bus structure 17, andmicroprocessor 11 is configured to drive memory bus 17.

A battery 15 is the power source in the stand-alone mode, and may berecharged in one or more of several ways. The power traces are not shownin FIG. 3, but extend to all of the powered devices in the μPDA module.When the unit is docked in the host, the host power source may beconnected to pins through the host interface to recharge the battery.Alternatively, an attached means such as a solar panel may be configuredto charge the battery and/or provide power to the μPDA. A solar panelfor power is described elsewhere in this disclosure. Also the batterymay be easily removed for periodic replacement.

Host bus connector 14 is a part of a host interface which comprises abus structure 26 for providing connection to the host in docked mode, asdescribed above. In a preferred embodiment, the host interface isaccording to PCMCIA Type II, Rev. 3 standard, which is capable ofcommunication either in PCMCIA mode or in a mode similar to PCI mode.PCI mode refers to a high-speed intermediate bus protocol beingdeveloped by Intel corporation, expected to become a standard busarchitecture and protocol in the industry. The physical interface at thehost in this embodiment is a slot-like docking bay, as is typical ofknow docking bays for PCMCIA devices. This docking bay may beimplemented as a docking box, a built-in unit like a floppy-drive unit,or it may take some other form.

Connector portion 20 is a part of the expansion bus interface describedabove, comprising a dedicated bus structure 40 connected tomicrocontroller 11. This interface can be implemented in a number ofdifferent ways. The purpose of the optional expansion bus interface isto connect to optional peripheral devices, such as a printer, a FAXmodem, a host cellular phone, and others. The expansion bus interface isnot an essential feature in a minimum embodiment of the presentinvention, but provides vastly enhanced functionality in manyembodiments.

The expansion interface can take any one of several forms. A preferredform is an extended enhanced parallel port and protocol based on aninvention by the present inventors disclosed in a copending patentapplication. Another form is an indexed I/O port having 8-bit addressand 8-bit data capability. The requirement of the expansion port is thatthe connection and communication protocol be compatible with expansiondevices, such as telephone modems, fax modems, scanners, and the like.Many other configurations are possible.

Optional equipment such as devices listed in box 19 may be connected foruse with the μPDA through the expansion bus. Selected ones of suchdevices may also be built in to the μPDA in various embodiments,providing variations of applicability. In the former case, connection isthrough path 21 and the expansion bus interface via connector portion20. In the built-in case, connection is in the interconnection traces ofthe μPDA as indicated by path 23.

I/0 interface 16 (also FIG. 1B) is for viewing μPDA application-relateddata and for touch-sensitive input via softkeys. By softkeys is meantassignment by software of various functions to specific touch sensitivescreen areas, which act as input keys. Labels in I/O interface 16identify functionality of the touch-sensitive areas in various operatingmodes according to installed machine control routines. LCD display 25and the touch-sensitive area 27 together form the combination I/Ointerface 16 described also above.

In some embodiments of the present invention, data and program securityis provided comprising an Electrically Erasable Programmable Read OnlyMemory (EEPROM) 31, which is connected by dedicated communication linesto microcontroller 11. EEPROM 31 holds one or more codes installed atthe point of manufacturing to provide security for information transferbetween a host and a μPDA. The purpose is to control access by a host tothe memory contents of a μPDA, so each μPDA may be configured to anindividual. To accomplish this, docking and bus mastering machinecontrol routines are initiated at the point of clocking, and thissecurity process is described in more detail below. In otherembodiments, security codes may be provided by a Read Only Memory (ROM)chip or other permanent or semi-permanent memory source.

FIG. 4 is a plan view similar to FIG. 1B, of a μPDA, showing inparticular I/O interface 16. The size and location of I/O interface 16may vary, but in general occupies a major portion of one of the sides ofthe module. In one embodiment I/O interface 16 comprises an LCD displaywith a resolution of 256 by 144 pixels in a screen size that displays 32by 12 characters. Each character in this embodiment is displayed in anarea eight pixels wide and twelve pixels high. In another embodiment,the pixel resolution is 320 by 200, which corresponds to 40 by 16characters.

The touch-sensitive areas of the touch-sensitive screen correspond tothe character areas of the display. By touching an area with a finger orstylus, data can be entered quite quickly and with minimal CPU demand.

At one corner, thumbwheel 18 provides a two-directional means ofcontrolling the configuration of the display according to installedcontrol routines. A menu 70 is configured at one side to represent thecurrent status of any application in progress and to provide appropriateuser menu selections. In a preferred embodiment input from thumbwheel 18is used for scrolling through menu 70, and active areas may be indicatedby a cursor. A user makes a menu selection by pressing the appropriatetouch-sensitive area. A specific input may be provided to cause the menuarea to be displayed on either side of the display according to a user'spreference.

Specific characters are displayed in this embodiment in a region 74,with each character area associated with a touch-sensitive input area.As region 70 dedicated to selectable characters is much too small todisplay all characters of a standard keyboard, input from thumbwheel 18allows a user to pan region 74 displaying an entire virtual standardkeyboard. Movement of thumbwheel 18 in one direction pans the characterregion horizontally, and movement in the other direction pans thecharacter region vertically. When an end is reached the window pans ontothe virtual keyboard from the other end. In this manner, a user mayquickly pan the character window to display an entire standard keyboard,and make selections with a finger or a stylus. Of course, it is notrequired that a virtual keyboard be laid out for access in the format ofa standard keyboard. Characters and punctuation, etc., could just assimply be displayed in a single strip along a region of the display, andscrolled by input from the thumbwheel or other pointer-type inputdevice.

In this embodiment, to avoid delays caused by panning, if the thumbwheelis rotated quickly the character window jumps rather than scrolling tospeed up the interface. In addition, menu 70 may optionally provide fora character display in different fonts and sizes, although a single fontis preferred to minimize memory demand. It will be apparent to thosewith skill in the art that there are many alternatives for characterselection and display, and many ways thumbwheel 18 may be configured toallow for scrolling and panning.

A document window 72 is provided in this embodiment at the top or bottomof I/O interface 16. A cursor locates the active position within thedocument for editing purposes. Menu 70 provides selection of availablefonts, and input by thumbwheel 18 controls cursor movement over thedocument. As a document will in almost all cases be much larger than thedisplay capability of region 72, it is necessary to pan the documentwindow in essentially the same manner as the keyboard window is panned.For example, rotating thumbwheel 18 in one direction may displayhorizontal strips of a document, while rotating the thumbwheel in theopposite direction moves the window vertically strips of the samedocument.

A soft key or optional hard key may be configured to switch between thedocument and keyboard window, and the same or another key may beconfigured to switch between scrolling left or right, up or down,document or keyboard. A switch key may be used to change the thumbwheelmode of operation. A switch key may also be used in combination with afloating pointer to select characters and menu items. In thisembodiment, the user can keep his or her hands relatively stationary onjust the thumbwheel and the switch key, making all possible selections.Use of a switch key in combination with a floating pointer facilitatesthe use of small fonts. A switch key may also be incorporated as anadditional hard key in a convenient location on the case 12.

It will be obvious to a person skilled in the art than there arenumerous ways to combine menu selections, switching keys and I/Oconfigurations to provide a user-friendly user interface. A furtherembodiment of the present invention provides an I/O set-up applicationwherein a user may completely customize features of I/O area displays.

There are other sorts of mechanical interfaces which may be used toprovide pointer-style input in different embodiments of the invention asalternatives to the thumbwheel disclosed. One is a four-wayforce-sensitive mouse button and a selector button, which may be locatedat opposite ends of case 12 below I/O interface 16. Each button isdesigned to be operated by one finger. The four-way force-sensitivemouse button can provide menu scrolling of a cursor and panning and/orindexing of keyboard and document windows, while the selector button isused to select and edit according to position of a cursor. Thisconfiguration minimizes hand movement and keeps the I/O area clear forviewing.

Implementation of thumbwheels, pressure-sensitive switches and buttons,and the like, are known in the art, including the translation ofmechanical motion and pressure to electrical signals and provision ofsuch signals to a microcontroller. For this reason, details of suchinterfaces are not provided in this disclosure. Combinations of suchinputs with displays and input areas may, however, be considered asinventive.

FIG. 5 is an isometric drawing of a μPDA 10 in position to be docked ina notebook computer 172 via a Type II PCMCIA docking port 105 accordingto an embodiment of the present invention. As further described below,once the μPDA is docked, it is activated and a procedure is initiatedwith the host computer to manage communication and verify memory accessrights (security).

Access rights are considered important by the inventors for a number ofreasons. Firstly, through the expedient of one or more specific codes,unique to each μPDA, a user may protect files stored in his module fromaccess by unauthorized persons. The code can be used both to controlaccess to data and files via I/O interface 16, and also through the hostbus interface, so data and files may be secure from access by anunauthorized host system.

In the former case, when a μPDA is powered up, an application routinecan query the user for an access code to be entered at I/O interface 16FIG. 4). If the code is not entered properly, access is denied, andpower goes off. Codes for the purpose are stored in EEPROM 31 (FIG. 3),or in whatever ROM device may be devoted to the purpose. In someembodiments, the code may by mask-programmed at manufacture, so it isnot alterable. In others, the code may be accessible and changeable byspecial procedures in the field.

In the case of host communication, it is possible that a portable ordesktop computer, or some other device, may have a docking portphysically configured to receive a μPDA, yet not be configured tocommunicate with the μPDA. This certainly might be the case where theμPDA is in the PCMCIA form. For purposes of disclosure and description,this specification terms such a unit a generic host. If the unit isconfigured to communicate with a μPDA it is an enabled host. If a hostis configured for full access to a particular μPDA, it is a dedicatedhost.

If a docking unit is a generic host, there will be no communicationunless the person presenting the μPDA provides the control routines tothe host. This may be done for a generic host such as by transfer from afloppy disk, from a separate memory card through the docking port, or,in some embodiments, the communication software may be resident inmemory 13 (FIG. 3) of a docked μPDA, transferrable to the host tofacilitate further communication.

If the docking unit is in fact an enabled host, or is configured afterdocking to be an enabled host, the stored code or codes in EEPROM 31 (orother storage unit) may be used to verify authorization for data andprogram transfer between the host and a μPDA. In one embodiment thisprocedure is in the following order: First, when one docks a μPDA in acompatible docking port, certain pin connections convey to both the μPDAmicrocontroller and to the host CPU that the module is docked. Assumingan enabled host, the fact of docking commences an initializationprotocol on both systems.

In most embodiments, if the docking unit is a non-host, that is, it isnot capable of communication with the docked module, nothing happens,and the user may simply eject the docked module. If the computer is anenabled host, an application is started to configure host access to theμPDA's data files through the μPDA microcontroller. A user interface,described more fully below for a particular embodiment, is displayed onthe host monitor 104 (FIG. 5). The host interface menu, as well as otherapplication menus, may be formatted in part as a display of the μPDA I/Ointerface 16 as seen in FIG. 4 and described in accompanying text. Insome embodiments, the docked μPDA can be operated in situ bymanipulating the input areas of the μPDA displayed on the host's screen.

If the host is not a home unit for the docked module, that is, the hostdoes not have matching embedded ID codes to those stored in the dockedmodule, a visitor protocol is initiated. In this event, a visitor menuis displayed on host display 104 for further input, such as passwordqueries for selections of limited data access areas in the dockedmodule. In this case, too, a user may gain full access to the dockedmodule's memory registers by entering the proper password(s).

If the host is a fully compatible host home unit, full access may beimmediately granted to the host to access memory contents of the dockedmodule, including program areas; and both data and programs may beexchanged.

In any case, when the μPDA is ejected or otherwise removed from thedocking port, the on-board module microcontroller again gains fullcontrol of the internal μPDA bus structures.

FIG. 6 is a simplified block diagram of a μPDA docked in a hostcomputer, and FIG. 7 is a basic logic flow diagram of the steps involvedin docking a μPDA in a host computer 66 according to an embodiment ofthe present invention. Host computer 66 is represented in a mostlygeneric form, having a host CPU 24, and input device 60, such as akeyboard, a mass storage device 28, such as a hard disk drive, andsystem RAM 62. It will be apparent to those with skill in the art thatmany hosts may have a much more sophisticated architecture, and thearchitecture shown is meant to be illustrative.

When a μPDA unit is docked, connector 14' in FIG. 6 comprises portion 14shown in FIGS. 1B and 3 and a mating connector portion for engagingportion 14 in port 105 (FIG. 5). The engagement of the separate portionsof the connector cause bus 26 in the μPDA and bus 26' in the host tobecome directly connected. There is then a direct bus path betweenmicrocontroller 11 and host CPU 24 (FIG. 6).

As previously described there is a pin configuration (not shown) inconnector 14 dedicated to signalling that a module is docked. In FIG. 7,step 42 represents insertion of a μPDA module into the docking port. Atstep 44 the signalling pin configuration signifies physical docking isaccomplished. At step 46 host interface bus 26 is activated, includingthe mated host bus 26' in the host.

At step 48 (FIG. 7) microcontroller 11 in the μPDA starts apreprogrammed POST procedure. Microcontroller 11 in this embodiment hasa page of RAM 68 implemented on the microcontroller chip. In otherembodiments RAM may be used at other locations. At step 50, the POSTroutine loads a bootstrap program to RAM 68, which includes a code orcodes for security matching. This code or codes comprise, for example, aserial number.

At step 54 the bootstrap program begins to execute in microcontroller11, and at step 56 the microcontroller looks for a password from thehost on host interface bus 26 (FIG. 6).

The fact of docking, assuming an enabled or dedicated host, also causesa communication routine, which may be accessed from, for example, massstorage device 28 at the host, to display a user interface on monitorscreen 104 of the host unit, as partly described above. It is thiscommunication program that makes a generic host an enabled host.

Assuming an enabled, but not dedicated, host, the user interface willquery a user for input of one or more passwords, after successful entryof which the host will pass the input to microcontroller 11 forcomparison with the serial number and perhaps other codes accessed fromEEPROM 31 in the bootstrap of the μPDA.

According to the codes passed from the host to the docked module,microcontroller 11 will allow full access to memory 31 at function 52,FIG. 7, for the host CPU, or limited access at some level at function58, defined by received codes (or no matching code at all).

The access protocols and procedures allowing partial or direct access toμPDA memory 13 are relatively well known procedures in the art, such asbus mastering techniques, and need not be reproduced in detail here. Inaddition to simple comparison of codes, there are other techniques thatmay be incorporated to improve the integrity of security in thecommunication between a μPDA and a host. For example, within thelimitation of storage capacity of the EEPROM or other nonvolatilesource, executable code might also be uploaded to onboard RAM 68, orcode keys to be used with executable code from other sources, orrelatively simple maps re-allocating memory positions and the like, soeach μPDA may be a truly unique device.

There are additional unique features provided in one aspect of theinvention as part of the communication routines introduced above. Onesuch feature is automatic updating and cross-referencing of existingfiles and new files in both computers, under control of the host system,with the host having direct bus access to all memory systems.Auto-updating has various options, such as auto-updating by clocksignature only, flagging new files before transfer, and an editing meansthat allows the user to review both older and newer versions of filesbefore discarding the older in favor of the newer. This automatic orsemiautomatic updating of files between the satellite and the hostaddresses a long-standing problem. The updating routines may alsoincorporate a backup option to save older files.

Another useful feature in host/μPDA communication is a means for a userto select and compose a mix of executable program files for downloadingto a μPDA, either replacing or supplementing those executable routinesalready resident. A user can have several different program lists fordownloading as a batch, conveniently configuring the applicability of aμPDA among a wide variety of expected work environments.

Such applications as databases, spreadsheets, documents, travel filessuch as currency converters, faxing and other communications programs,time clocks, address and telephone records, and the like, may comprisecustomized lists of user-preferred applications.

In another embodiment, an undocked μPDA can transfer data via theoptional expansion bus 40 (FIG. 3) directly to a host. In the specialcase of a μPDA user without access to a PCMCIA interface on his host(notebook or desk-top) computer, he or she can connect to a host via anauxiliary port on the host, such as a serial port, via the expansion businterface. In this case, the μPDA still requests password(s) from thehost, and controls access to its on-board memory according to thepassword(s) received.

The optional expansion interface may also be used in some embodimentswhile a μPDA is mastered by a host, wherein the host may effectivelysend data through the bus structures of the μPDA.

Additional Aspects and Features

Software Vending Machine

In a further aspect of the invention, a Software Vending Machine with avery large electronic storage capacity is provided, wherein a μPDA usermay dock a module and purchase and download software routines compatiblewith the μPDA environment.

FIG. 8 is an isometric view of such a vending machine 61 having adocking bay 63 for a μPDA, a credit card slot 65, and a paper money slot67. A display 69 provides a user interface for reviewing and purchasingsoftware from the vending machine, along with selector buttons such asbutton 71 along the sides of the display. In an alternative embodimentthe display may also have a touch screen, and may, in some embodiments,emulate the μPDA I/O area on a larger scale.

In operation, a user may, in this embodiment, review software for salesimply by docking his μPDA unit in the vending machine and selectingfrom a menu on display 69. The menu may allow the user to browse allavailable applications, or list new applications since entered dates.The user can select certain applications, try them out, at least insimulation, and then select applications to purchase.

The vending machine, once all the requirements are met, such as properidentification and payment, copies the selected application(s) to thememory of the μPDA, or, alternatively, to a floppy disk provided byeither the user or the vending machine. In this case there is also afloppy disk drive 73 in the vending machine and a port 75 for dispensingformatted floppies for a customer to use in the disk drive. This mode isuseful for the instances where a user's μPDA is loaded beyond capacityto receive the desired software, or the user simply wishes to configurethe software mix himself from his or her own host computer.

There may also be provided a backup option so a user may instruct thevending machine to read and copy all or a selection of his files to oneor more floppy disks before installing new files or data.

As described above, each user's μPDA includes an EEPROM or other storageuniquely identifying the μPDA by a serial number or other code(s), sothe vending machine may be configured in this embodiment to provide thesoftware in one of several modes.

A user may buy for a very nominal price a demo copy of an application,which does not provide full capability of the application, but will givethe user an opportunity to test and become familiar with an applicationbefore purchase. Also, the user may buy a version of the sameapplication, configured to the ID key of the μPDA to which it is loaded,and operable only on that μPDA. In another embodiment, the software istransferable between a family of keyed μPDAs, or has the ability to"unlock" only a limited number of times. In these cases, theapplications would be sold at a lesser price than an unlocked version.The unlocked version works on any μPDA and/or host/μPDA system. Thehigher price for the unlocked version compensates for the likelihood ofunauthorized sharing of the vended applications.

The vending machine could also offer a keyed version, customized tooperate only on the μPDA docked in the software vending machine, or upona family of μPDAs. This keyed version is possible because of theindividual and unique nature of each μPDA, which has, at a minimum, aunique serial number, and may also have other security programming, asdescribed above, which allows a vending machine to prepare and downloada customized copy of an application that will operate only on theparticular module for which it is purchased.

There are a number of different means by which unique correspondencemight be accomplished, as will be apparent to those with skill in theart. A standard version stored in the memory facility of a vendingmachine might be recompiled, for example, on downloading, using a uniquecode from the docked or identified μPDA as a key in the compilation, soonly the specific μPDA may run the program by using the same unique keyto sequence the instructions while running. The key for scrambling orotherwise customizing an application might also comprise other codesand/or executable code sequences stored uniquely in a μPDA.

In yet another aspect related to the vending machine, there is a printeroutlet 77 which prints a hardcopy manual for the user. It is, of course,not necessary that the software vended be specific to the M-PDA.Applications may also be vended for other kinds of machines, andtransported in the memory of the μPDA, or by floppy disk, etc. In thisembodiment a non-μPDA user can acquire a wide assortment of software.

The software vending machine may also serve as an optional informationaldisplay center in such locations as airports, train stations, conventioncenters, and hotels. Upon inserting a μPDA a user may interface directlyand upload current information including, but not limited to, local,national, and world news; stock quotes and financial reports; weather;transportation schedules; road maps; language translators; currencyexchange applications; E-mail and other direct on-line services.

A customized vending machine could be tailored to business travelers andallow fast access to pertinent information, allowing the user todownload files to send via E-mail. In another aspect of the invention,the vending machines are linked to each other allowing users to sendmessages to associates travelling through locations of associatedvending machines. Such dedicated μPDA E-mail is immediately downloadedto a specific μPDA as it is docked. The sender may have the associate'sμPDA unique encoded key as identification, or some other dedicatedidentifying means for E-mail.

In another embodiment, as each business associate arrives at an airport,he or she may prompt the custom vending machine in that location via anoptional installed infrared interface (not shown) in their μPDA. Thecustom vending machine, also equipped for infrared communication,receives the signal and sends/or receives any messages that are waiting.

Enhanced Display

FIG. 9 is a plan view of an enhanced I/O interface unit 79 according toan aspect of the present invention. Interface unit 79, with about a5-inch diagonal measurement, comprises a combination LCD display atleast partially overlaid by a touch-sensitive input screen, providing anI/O area 80 in much the same manner as in a μPDA. Four docking bays 81,83, 85, and 87 are provided in the left and right edges of interfaceunit 79 in this embodiment, and are configured for PCMCIA type IImodules. One of these bays may be used for docking a μPDA according tothe present invention, and the other three to provide a larger CPU,additional memory, battery power, peripheral devices such as modems, andthe like by docking functional PCMCIA modules.

Interface unit 79 is a framework for assembling a specialty computerthrough docking PCMCIA units, including a μPDA according to the presentinvention. In other embodiments where the μPDA assumes other formfactors, the docking bays may be configured accordingly.

A clocked μPDA in this embodiment is configured to produce its I/Odisplay on I/O area 80. The thumbwheel on the M-PDA is accessible whiledocked and acts as described above in the stand-alone mode in this case.In another aspect, the enhanced display has a re-configured output thatenables the user to manipulate the data from the touch-screen aloneand/or additional hardware selector buttons and/or a standard keyboardattached to the enhanced display via a dedicated bus port, or eventhrough the expansion port of a docked μPDA. In a further embodiment theenhanced display has a dedicated mouse port and/or a dedicatedthumbwheel.

In yet another embodiment, interface unit 79 has an inexpensive,conventional, replaceable battery and/or a rechargeable battery. Also,in another aspect, interface unit 79 may dock two or more individualμPDAs and cross-reference data files between them according to controlroutines that can manipulate mutually unlocked files. Further still,interface unit 79 may be placed and structurally supported for easyviewing on a dedicated standard or smaller-sized keyboard, connecting tothe keyboard as an input device. The keyboard would then automaticallyserve as the input device.

Interface unit 79 for a μPDA is small and compact enough to slip into apocket book or briefcase, providing a very portable, yet very powerful,computer.

Migrophone/Voicenotes

FIG. 10 is a plan view of a μPDA 110 with an I/O interface 116, anexpansion port 120, and a host interface connector 114. μPDA 110 has allthe features previously described and additionally a microphone 88. Inthis embodiment, control routines in the μPDA use a linear predictivecoding (LPC) approach to convert analog input from the microphone to adigital voice recording. This approach uses a minimum of memory, butstill is capable of reproducing audio input like the human voice withinrecognizable limits.

In an alternative embodiment, for better quality voice recording, atwo-step integrator may be used in order to separate the analog signaland synthesize a closer digital representation.

With a μPDA so configured, a user's voice notes can be recorded andlater uploaded to a host for processing. In future embodiments thedigital signals may be converted to text or sent as voicemail on anetwork. In yet another embodiment, the microphone is integrated with aspeaker for editing purposes.

Cellular Telephone Interface

FIG. 11 is an isometric view of a μPDA 10 docked in a dedicated cellulartelephone 45 according to an embodiment of the present invention.Telephone 45 has a docking port 49 for a μPDA according to theinvention. In this embodiment, port 49 is on one side of telephone 45,and there is a window 51 to provide access to I/O interface 16 of theμPDA after it is docked. With the μPDA docked, all of the software andmemory of the μPDA is available to the telephone and a user may operatethe phone by I/O interface 16.

In this aspect of the invention, unique control routines and displayconfigurations are provided to enhance use of the cellular phone. Forexample, all of the user's collection of phone numbers, associatedcredit card numbers, access codes, etc. are readily available and may bequickly and conveniently accessed and used. In one aspect, a simpleinput displays alphabet letters to select, and once a letter isselected, a partial list of parties that might be called is displayed.One may scroll through the list by touch input or by use of thethumbwheel of the μPDA and select a highlighted entry. It is notrequired that the telephone numbers be displayed.

Once a party to be called is selected, the μPDA dials the call,including necessary credit card information stored in the memory of theμPDA for this purpose.

In a further embodiment, the calls are timed and time-stamped and acomprehensive log, with areas for notes during and after, is recorded.

In another embodiment, conversations are digitally recorded and filedfor processing later. A future embodiment may include a voicecompression program at a host or within cellular phone 45. Compressedvoice files, such as, for example, messages to be distributed in avoicemail system, may be downloaded into the μPDA or carried in a largermemory format inside the cellular telephone. The μPDA can then send thefiles via a host or dedicated modem attached at connector portion 20 tothe optional expansion bus 40 (FIG. 6).

The cellular telephone may, in this particular embodiment, have a busport for digital transmission. In this case, the compression algorithmalong with voice system control routines are also established at thereceiving end of the transmission to uncompress the signal anddistribute individual messages.

In a further embodiment, voice messages may be sent in a wireless formatfrom the cellular telephone in uncompressed digital synthesized form,distributing them automatically to dedicated receiving hosts, orsemi-automatically by manually prompting individual voicemail systemsbefore each individual message. In a further aspect of wirelesstransmission, a microphone/voicenote μPDA as in FIG. 10 may sendpreviously stored voicenotes after docking in a cellular telephoneinterface.

In Europe and Asia a phone system is in use known as CT2, operating on adigital standard and comprising local substations where a party with acompatible cellular phone may access the station simply by being withinthe active area of the substation. In one aspect of the presentinvention, a CT2 telephone is provided with a docking bay for a μPDA,and configured to work with the μPDA. In yet another aspect of theinvention, in the CT2 telephone system, and applicable to other digitaltelephone systems, a compression utility as disclosed above is providedto digitally compress messages before transmission on the CT2 telephonesystem.

It is roughly estimated that a dedicated compression algorithm maycompress ten minutes of voice messages into one minute using theexisting CT2 technology. This would save on telephone use chargessignificantly. In this aspect, there needs be a compatible decompressionfacility at the receiving station, preferably incorporated into astandard μPDA voicemail system for CT2 or other digital transmissions.

In a further embodiment, control routines are provided to enable themicrophone/voicenote μPDA as illustrated in FIG. 10 to carry digitalvoicenotes, either compressed or uncompressed. When docked in aCT2-compatible μPDA cellular telephone, the μPDA in this embodiment cantransmit the digital voicenotes in compressed form.

Speaker/Pager

FIG. 12 is a plan view of a μPDA 210 with a microphone/speaker area 90and a pager interface 92 according to an embodiment of the presentinvention. This μPDA has the ability to act as a standard pager, pickingup pager signals with installed pager interface 92 and alerting a userthrough microphone/speaker 90. Once the signals are received, μPDA 210can be docked in a compatible cellular telephone as illustrated in FIG.11 and the μPDA will automatically dial the caller's telephone number.All other aspects are as described in the docked mode in the cellulartelephone.

In another embodiment, the speaker/pager μPDA can be prompted togenerate DTMF tones. The DTMF tones are generated from a caller'stelephone number.

The speaker/pager μPDA can store pager requests in its onboard memory.It can also display all pager requests including time and date stamps,identification of the caller, if known, and other related information,on I/O interface 216. In this particular embodiment, a user can receivea page, respond immediately in digital voicenotes on the μPDA viaspeaker/microphone 90, and then send the response from a dedicatedμPDA-compatible cellular telephone or conventional telephone.

Wireless Infrared Interface

FIG. 13 is a plan view of a μPDA 310 with an IR interface 94 accordingto an embodiment of the present invention. In this embodiment the μPDAmay communicate with an array of conventional appliances in the home oroffice for providing remote control. Unique signals for the appliancesare programmed into the μPDA in a learning/receive mode, and filed withuser password protection. Once a correct password in entered, anicon-based menu is displayed on I/O area 316 in a user-friendly format.A master routine first queries a user for which device to access. Forexample, in a residential application, icons are displayed for suchthings as overhead garage doors, security systems, automatic gates,VCRs, television, and stereos.

In another aspect of the invention, a receiving station such as a hostcomputer or peripheral interface has IR capabilities to communicate datadirectly from a nearby μPDA with an infrared interface. In a furtherembodiment the μPDA may interface in a cellular network and act as awireless modem.

PERIPHERALS

A μPDA may serve as the platform for various peripheral attachments viaexpansion port 20 (FIG. 1B and others). Upon attachment to a peripheral,a dedicated pin or pins within expansion port 20 signal microcontroller11, and a peripheral boot-strap application is executed. Interfacingcontrol routines, which may reside in the peripheral or in the memory ofthe μPDA, are then executed, and the μPDA I/O interface displays therelated menu-driven options after the linking is complete.

Scanner

FIG. 14 is a plan view of a μPDA 10 with a scanner attachment 55according to an embodiment of the present invention. The scannerattachment is assembled to the μPDA, making electrical connection viaexpansion port 20. In this embodiment the physical interface of thescanner is shaped to securely attach to the μPDA. Scanner attachment 55has a roller wheel 57 or other translation sensor, which interfaces withwheel 18 of the μPDA, providing translation sensing in operation for theresulting hand-held scanner. In another aspect, scanner attachment 55has a translation device which transmits the proper signal throughexpansion port 20. The scanner bar is on the underside, and one or morebatteries 59 are provided within the scanner attachment to provide theextra power needed for light generation.

In the scanner aspect of the invention, scanner attachments 55 ofdifferent width D2 may be provided for different purposes. The bar maybe no wider than the μPDA, or may be eight inches or more in width toscan the full width of U.S. letter size documents, or documents oninternational A4 paper. Unique control routines display operatinginformation on the μPDA's I/O area 16 for scanning, providing a userinterface for setup of various options, such as the width of the scannerbar, and providing identification for files created in the μPDA memoryas a result of scan passes. Scanned data stored in the μPDA memory maybe quickly transferred to the host via host interface 14 when the μPDAis docked. Unique routines may be provided to automate the process, sothe user does not have to search for files and initiate all of thetransfer processes.

Facsimile Option

FIG. 15 is a plan view of a μPDA with a fax-modem module 89 attachedaccording to an embodiment of the present invention. A fax andtelecommunication capability is provided via conventional telephonelines to the μPDA by fax-modem 89 interfacing to expansion bus interface20. The fax-modem has internal circuitry for translating from the busstates of the expansion bus to the fax protocol, and a phone pluginterface 91. In another aspect, the μPDA can be docked in a host and beused in combination with fax-modem 89 to provide faxing and filetransfers of both host and μPDA data files. In this case, the fax-modemroutines are displayed on the host monitor.

Printer

FIG. 16 is a plan view of a μPDA with a Centronics adapter interfaceaccording to an embodiment of the present invention. A printer connector93 engages expansion interface 20 by a connector 95 through a cable 97.Translation capability resides in circuitry in connector 93, which isconfigured physically as a Centronics connector to engage a standardport on a printer.

Barcode Reader and Data Acquisition Peripheral

FIG. 17 is an isometric view of a μPDA 10 docked in a barcode reader andacquisition peripheral 100 according to an embodiment of the presentinvention. μPDA 10 is docked in docking bay 149. I/O interface 16displays information through opening 147 according to specialized dataacquisition applications. In this particular embodiment peripheral 100has an IR interface 94, a microphone 103, a scanner port 101 (riotshown), battery pack 105, and a numeric keypad pad 96 implemented as atouch-sensitive array.

Application routines enable the data acquisition peripheral to operateas, for example, a mobile inventory management device. The user may scanbarcode labels with scanner 101 and enter information, such as counts,on keypad 96 or by voice input via microphone 103. Since applications ofperipheral 100 are very specialized, only a limited voice recognitionsystem is needed. The voice recognition system may prompt other commandroutines within the master applications as well.

As inventories are collected, the database may be displayed and alsomanipulated directly via I/O area 16 in open bay 147, or information maybe downloaded at a prompt to a nearby host via IR interface 94.

Alternatively to frequent data transmission, data may be stored or anauxiliary option memory location in peripheral 100.

In another aspect, the data acquisition peripheral may be interfaced tothe analog output of a monitoring device, such as a strip chartrecorder, and may digitize and store the incoming analog signals.

Solar Charger

FIG. 18 is an isometric view of the side of a μPDA 10 opposite the I/0interface with a solar charger panel 98 according to an embodiment ofthe present invention. Panel 98 is positioned so that when μPDA 10 is instrong light, such as sunlight, the solar charger absorbs the solarenergy and converts it to electricity to recharger battery 15 inside theμPDA. Solar charger 98 may be permanently wired to the circuitry of theμPDA or attached by other means and connected to a dedicated electricalport or the expansion port. The solar charger is placed so that the μPDAcan be fully docked in a docking port with the panel in place. Inanother aspect, a detachable solar charger may be unplugged beforedocking the μPDA, and the detachable charger may then be of a largersurface area.

Games/Conference Center

FIG. 19 is a largely diagrammatic representation of a Games Center unit33 according to an aspect of the invention for connecting several μPDAunits (37, 39, 41, and 43) together to allow competitive and interactivegames by more than one μPDA user. Games Center unit 33 is controlled byan 80486 CPU in this particular embodiment. μPDAs may be connected tothe central unit by cable connection via the expansion bus or the hostinterface of each μPDA, through a connector such as connector 35. Thedrawing shows four connectors, but there could be as few as two, and anyconvenient number greater than two.

As a further aspect of the present invention, the gaming center mayserve as a conference center where a number of μPDAs may exchangeinformation. In this way, for example through custom routines stored andexecutable in central unit 33, a manager may update a number ofsalespeoples' μPDAs, including but not limited to merchandise databases,spreadsheets, price sheets, work assignments, customer profiles, addressbooks, telephone books, travel itineraries, and other related businessinformation while in conference.

Standard Keyboard

FIG. 20 is an isometric view of a keyboard 151 connected by a cord andconnector 153 to a μPDA 10 via the expansion port 20. In this example,the keyboard is a mechanical keyboard having a full-size standard keyarray and an on-board controller and interface for communicating withthe μPDA. In other embodiments the keyboard may take many other forms,including a two-layer, flexible, roll-up keyboard as taught in U.S. Pat.No. 5,220,521.

In addition to keyboards, other input devices, such as writing tabletsand the like may also be interfaced to a μPDA via expansion port 20.

There are numerous additional ways to combine different embodiments ofthe μPDA for useful functions. For example, an IR-equipped μPDA attachedto scanner 55 may transfer large graphic files in near real time to ahost computer. If the files were of text, the host may further processthe files automatically through an optical character recognition (OCR)application and send the greatly reduced ASCI files back to the μPDA. Asdiscussed above, the μPDA family of devices establishes a protocol ofsoftware security and distribution as well as having the ability to bebus mastered by a host computer system for numerous applications.

Removable Pointer Devices

One of the difficulties faced in the design and development of aminiature computer product, such as a hand-held μPDA as described inmuch detail above, is in the implementation and connection of inputdevices. Pointer devices fall into this category, and a number of uniqueoptions and alternatives are described herein below for pointer devicesstorable in and deployable from portable computers. The descriptionsbelow are illustrated primarily with reference to what are known asnotebook-type computers, but are considered by the inventors to beequally applicable to hand held devices such as the μPDA devicesdescribes in this specification.

FIG. 21A is an isometric view of a notebook-type computer 1010 with acompartment 1012 having a closure 1018, for storing a pointer device1014 when the pointer is not needed. The compartment is shown on oneside of the housing of the computer, but could as easily be locatedelsewhere, and there a variety of ways the closure could be provided.The pointer may be any one of many sorts, such as joystick, trackball,or mouse device.

FIG. 21B is an isometric view similar to FIG. 21A showing a mouse-typepointer device 1020 deployed for use from compartment 1012, andconnected to the host computer by a cable 1022. The cable may be storedin this case in compartment 1012 along with the pointer device. Thereare also alternative ways the cable might connect, such as at a parallelor a serial port on the host.

FIG. 21C is an isometric view of a notebook computer showing a cordlessmouse device 1022 storable in compartment 1012 and deployed for use.There are several ways communication may be handled for the pointerdevice in this embodiment. In the embodiment of FIG. 21C the pointer hasan infra-red transmitter and the host has an infra-red receiver 1024.

FIG. 21D is an isometric view of a notebook computer showing a trackballpointer device 1028 connected to the host by a cable 1030. Thecommunication system in this case is the same as for a mouse-type deviceas described above.

FIG. 21E is an isometric view of a notebook computer showing a cordlesstrackball device 1032 deployed for use. The cordless trackball in thisembodiment employs an infra-red coded transmission system sending codeaccording to trackball movement to receiver 1024 at the host.

FIG. 21F is an isometric view of a notebook computer showing acombination pointer/trackball device 1034 deployed for use and connectedby a cable 1036 to the host. This device is a combination deviceoperable as a trackball in one orientation, and as a mouse device wheninverted so the trackball may make contact with a flat surface. Furtherdetails of the combination are described below with reference to FIGS.25 A-D.

FIG. 21G is an isometric view of a notebook computer showing acombination trackball/pointer device 1038 with cordless communication,and deployed from compartment 1012 for use. In this case, thecommunication system is infra-red, and there is a receiver 1024 on thehost.

FIG. 21H is an isometric view of a general-purpose portable computer1011 with a removable pointer device 1017 according to an embodiment ofthe present invention. Computer 1011 comprises a housing 1015 and atilt-up display 1013. The computer housing encloses standard electronicoperating elements, such as a CPU microprocessor and system RAM, notshown in FIG. 21H. There are connectors (not shown) to serial devicesand the like, which are typical for portable computers. A keyboard unit1019 provides a for user input. Removable pointer device 1017, inset inwell 1016 in the housing, comprises a trackball design including arotatable ball 1021 to transmit directional information to the host,left and right control buttons 1023 and 1025 for discrete signalling,and a drag control button 1027. The purpose of drag control button 1027is to signal that trackball movement is to be directed toward draggingan onscreen virtual object, a procedure well known in the art. Concavedepressions 1029 and 1031 on opposite sides of well 1016 allow space fora user to grasp the removable pointer device to snap it in and out ofthe well so it can be used as a separate unit.

The transmission medium between removable pointer and host in thisembodiment is infrared, which is transmitted from a light-emitting diode(LED). Two photodiode receivers are imbedded in the computer housing,one in a wall of the well for stationary mode reception (not shown inFIG. 21H) and one receiver 1033 in the front of the housing for portablemode reception. The photodiode receivers are connected with a commoncircuitry within the host computer.

FIG. 21I is an isometric view of computer 1011 with pointer device 1017removed from the well in the housing, deployed for use external to thehousing.

FIG. 22 is a plan view of removable pointer device 1017, showing LEDtransmitter 1024 inside the device facing photodiode receiver 1026inside a wall of well 1016. In the side walls of well 1016, concavedepressions 1029 and 1031 allow a user to grasp removable pointer device1017 and snap it in or out of well 1016. The removable pointer device isheld in place in this embodiment by light resistance provided byspring-loaded ball/detent pairs 1035 and 1037 on both sides of thedevice. Spring loading may originate from either the pointer device orin the wall of the well. Vertical guide rails along the well walls, notshown in FIG. 22, allow detents 1035 and 1037 to slide smoothly into thewell and snap into place once seated. The method of docking and latchinga removable pointer device into a location in the computer host is notlimited to the description for this embodiment. There are known in theart many other equivalent ways that can satisfactorily perform such afunction. For instance, instead of the pointer device being seatedsquarely in the well, the device can be inserted at a slant into thewell and snapped down into a spring-loaded base. The device can bereleased by the user pressing an indentation near the base of thedevice. Another variation is for the well to open to the front of thehousing so the pointer device can slide in and out on guide rails.Spring-loaded detents along the sides hold the device in place while itis docked in this embodiment.

FIG. 23 is a mostly diagrammatic representation of the internalcomponents of removable pointer device 1017 for the embodiment describedfor FIGS. 21 and 22. Two rollers, 1045 and 1047, are mounted at rightangles and bear against trackball 1021. As trackball 1021 rotates,roller 1045 responds to movements in a first direction and roller 1047senses movements at 90 to the first direction. The rollers are connectedto encoder wheels 1049 and 1051, which transmit signals relative tomovement to controller 1065.

Removable pointer device 1017 is powered by a battery 1062 that isrechargeable in this embodiment by charger circuit 1060 when the pointerdevice is seated in well 1016. Battery charger 1060 receives electricalcurrent from the computer host through a spring-loaded contact base, orany other suitable type of charging contact. In this embodiment a springwiper contact 1043 is located on one side of the well and a fixedcontact 1041 is on the side of the pointer. Contacts are well known inthe art and there are many equivalent ways that such a contact can beconfigured. For example, in other embodiments there may be a femaleconnector on the bottom of the pointer device that plugs into a maleconnector in the bottom of the host well. Such an arrangement not onlyserves as an electrical contact, but also holds the pointer device inthe well, minimizing or eliminating the need for detents.

Signals produced from the trackball's motion are converted to infraredsignals by microprocessor-based controller 1065 and output through LEDtransmitter 1024 to photodiode receiver 1026 in the well wall, or if thepointer is being used outside the well, photo diode receiver 1033 on thefront side of the housing as shown in FIG. 21. Input signals fromcontrol buttons 1023, 1025, and 1027 are also processed by controller1065.

FIG. 24 is a mostly diagrammatic representation of the internalcomponents of a cordless removable pointer device 1068 in an alternativeembodiment that uses magnetic induction as the medium of communicationbetween pointer device and host. All electromechanical components inFIG. 24 are the same as those described for the FIG. 23 configurationexcept electrical signals from the encoders and control buttons areinput by a microprocessor-based current controller 1090, which passesthe current through a one-turn generator loop 1070, creating a magneticfield represented by exemplary field lines 1071. Receiving loop 1072,which is located in the host housing, transmits a magnetically inducedcurrent to a demodulator 1073, which forwards the coded signal to acontroller.

There are a number of equivalent ways a receiving apparatus may beconfigured for reception by magnetic induction. For example, such anapparatus might be built into the case of the host computer, orimplemented on an add-on printed circuit board. Also, FIG. 24 is largelydiagrammatical, as stated above, and the transmission and receptor loopsare not drawn to actual size relative to other components. In general,both loops are much larger than shown, and there may be more than asingle turn in some embodiments.

In another embodiment of the invention, a cordless unit is providedhaving both stationary and portable mode features as described aboverelative to FIG. 21, and configured to operate both as a trackball and amouse device. In this embodiment one side of the combined removablepointer device is a typical trackball unit and when the device is turnedover, it may be used as a mouse. Operating mode is selected by a switchon the side of the device.

FIG. 25A is a plan view of a combined removable pointer device 1081.Pointer device 1081 comprises on the surface shown in FIG. 25A all theelements described for a trackball unit in the embodiment of FIGS. 21and 22, with the addition of an operating mode switch 1091 on one side.The user moves switch 1091 to select between trackball and mouseoperation. Trackball 1083, control buttons 1093, 1095, and 1089, LEDtransmitter 1099, and charging intact 1097 are located in the samepositions as are their counterparts in the removable trackball of FIGS.21 and 22.

FIG. 25B is a plan view of the opposite side of combined removablepointer device 1081. In this embodiment, control buttons 1101 and 1103are flush with the outside surface of the body of the pointer device, sowhen used as a trackball, the device can sit squarely on a desktopsurface or in its well. In a conventional trackball device, the rotatorball is not loosely mounted like that on a mouse so the ball does notnaturally fall to the desktop surface when the unit is inverted. Thisproblem is solved in the present embodiment by the relationship betweenthe height of protrusion of the three pushbuttons on the side oftrackball 1021, and the height of protrusion of the trackball.

FIG. 25C shows combination pointer device 1081 in contact with a flatsurface 1082. Dimension D3 from the casing to the outer surface of anyof the control buttons is greater than dimension D4 from the unit casingto the trackball. Slight pressure exerted on the unit causesspring-loaded control buttons 1089, 1093, and 1095 to depress bringingball 1083 into contact with surface 1082, so lateral movement will causethe ball to rotate.

The phenomenon of riding on the spring-loaded buttons provides a newaspect of control in operating the pointer device as a mouse. Forexample, in the often-occurring situation with a mouse where surfacearea available for mouse operations is limited, the mouse often has tobe picked up and repositioned on the operating surface. Picking up themouse so the ball does not touch the operating surface insures thatposition signals are not transmitted while the mouse is repositioned.With a mouse according to this embodiment of the present invention, themouse can be repositioned simply by relaxing the slight downwardpressure necessary to cause the ball to contact the operating surface.This seems at first encounter to be a small difference, but translatesto considerable advantage, especially in situations where the availableoperating surface is severely limited.

FIG. 25D is a mostly diagrammatic view of the internal components ofcombined removable device 1081. Internally the trackball and mouse inputcomponents share circuitry as shown for the removable pointer deviceembodiment in FIG. 23, with the addition of operating mode switch 1091and control buttons 1101 and 1103.

In alternative embodiments, either a removable trackball device or acombined trackball-mouse device as described above may be connected tothe host unit by a power cable. There are many ways a cable connectionmight be implemented for using such devices while removed from the wellon the host. For example, at some point on the case of the host computera small bay may have a cable electrically connected to the host bus andthe cable wound on a small reel with a connector on the outward end forconnecting to the pointer device when removed from the well. There aremany equivalent ways a cable connection might be implemented. In analternative embodiment, a pointer device sends polar coordinate locationsignals in response to movements made by a mechanically attached,extendable positional input bar. FIG. 26A is a plan view of such a polarcoordinate pointer device 1599 stored in unextended form inside acompartment 1597 in host housing 1595. Positional input bar 1501, whichpasses through a sensored pivot 1503, can be extended from opening 1500by the user pulling handle 1507. A preferred location for the device fora right-handed person is on the right side of the housing that containskeyboard 1594, but it could be located in any other place as well, suchas on the left side for left-handed users. Operational control buttons1596, 1597, and 1598 of the type typically used to control discretepointer signalling, are located in another area of housing 1595 in thisembodiment, such as on the left front side.

FIG. 26B is a plan view of polar coordinate pointer device 1599 inextended operating position. Positional input bar 1501 can be held byhandle 1507 and freely moved in a horizontal plane over an area adjacentto the computer housing. A stop near the inboard end of positional inputbar 1501 limits the maximum distance the bar can be extended. On theoutboard end of positional input bar 1501, a pivoted handle 1507 isattached by a vertical pin. Such a handle could have any of a number ofdifferent shapes.

In one embodiment, grooved channels (not shown) along the length of theinput bar engage mating guides in the pivot to prevent rotation of thebar around the longitudinal axis. There are a number of equivalent waysthe engagement and guiding function may be accomplished.

Sensors at pivot 1503, track radial displacement of positional input bar1501. Other sensors track rotation of the pivot mechanism, which is theangular displacement of positional input bar 1501. There are a number oftypes and arrangements of bar guides and sensors that would be suitable.Sensor information is transformed from polar coordinates to Cartesiancoordinates, and used as pointer input in the same fashion thattrackball or mouse positional input is used. Input from control buttons1596, 1597, and 1598 in FIG. 26A, is interpreted just as control buttoninput from a trackball or mouse device.

FIG. 26C is a graphic illustration of the geometry involved in thetransformation of displacement measurements of positional input bar 1501from R, Θ polar coordinates to x,y rectangular coordinates that can beused for screen cursor output. In FIG. 26C, points P₁ and P₂ representtwo x,y positions of pivoted handle 1507 on positional input bar 1501measured from pivot 1503 at P₀. Point P₁ is at radial distance R₁ andangle Θ₁ from P₀ ; point P₂ is at radial distance R₂ and angle Θ₂ fromP₀. The maximum radial distance, R_(max), the bar can be displaced isshown as a circular arc. Through transformation equations, x=R cos Θ andy=R sin Θ, x,y positions of both P₁ and P₂ points can be calculated.

There are a number of variations to the pointer described with referenceto FIGS. 26A, 26B, and 26C. For example, the pivot mechanism, bar, andhandle could all be a part of a mechanism dockable in the computer case,and removable as a unit to be placed external to the computer andoperated. In this alternative, the removable unit could be connected tothe host by a cable, or could communicate by infra-red or inductivetechniques.

FIG. 27A is a plan view of yet another alternative embodiment of thepresent invention, wherein a removable, cordless, pointer receivesbroadcast signals from multiple antennas in or on the host, and echosthe signals to a receiver in the host in a manner that allows controlcircuitry to track the position of the moving pointer. The trackedposition of the movable pointer is used in the manner that pointer inputfrom other types of pointers is used.

FIG. 27A shows one edge of a body 1311 of a host computer, having astorage compartment 1313 and three antennas 1315, 1317, and 1319. Amovable pointer device 1321 is storable in a compartment 1313 when notin use, and may be removed and deployed, as shown in FIG. 27A, for use.

FIG. 27B is a schematic of internal elements of device 1321, showing arectifier circuit of two antennas 1323 and 1329 connected withcapacitors 1325 and 1327, and a diode 1331. In operation in thisparticular embodiment, antennas 1315 and 1317 in the host are sendingantennas, and antenna 1319 in the host is a receiving antenna.

In one mode of operation, a carrier wave of a common frequency andamplitude is broadcast by each of sending antennas 1315 and 1317, butthe signals are broadcast at a pre-programmed phase shift. The rectifiercircuit in the pointer device intercepts the broadcast signals, combines(sums) them, and echoes a rectified waveform having a frequency known inthe radio arts as the Hull frequency. This signal is received at antenna1319, where connected circuitry analyzes the signal to determine theposition of the pointer relative to the broadcast and receivingantennas.

The receiving antenna intercepts both the original broadcast signals aswell as the echoed signal, but the broadcast signals are at a muchhigher and known frequency than the echoed signal, and are filtered.FIG. 27D is a simplified illustration of an echoed signal 1333 atreceiving antenna 1319.

Echoed signal 1333 exhibits an amplitude A_(e) and a frequency (1/t_(e))that are indicative of the position of the pointer device. The amplitudeis a function of the ratio of the distances to the pointer from each ofthe sending antennas, providing a locus, and the position on the locusis fixed by the frequency. The radio principles relied upon for thebroadcast cursor are well known in the radio arts, and are no moredetailed explanation is presented here.

The information contained in the echoed signal is sufficient to locatethe position of the pointer device near the host in essentially realtime, and circuitry to provide this information to the host computingelements in a manner to control a display cursor and the like, is wellknown.

FIG. 27C shows a broadcast pointer system comprising a host 1411, andthree antennas 1415, 1417, and 1419, similar to that shown in FIG. 27A,wherein a stylus 1421 is employed rather than a mouse-type pointer. Inthis embodiment the rectifier circuitry shown in FIG. 27B is implementedin a region 1423 near the point of the stylus. The stylus embodimentoperates in the same manner as does the mouse-type pointer describedabove, except the holding and manipulating of the pointer is in themanner of wielding a pen or a pencil, rather than a mouse. Thisembodiment provides a convenient way to input cursive writing andprinting to the host computer. With appropriate circuitry monitoring andinterpreting stylus movement, one may duplicate the functions of apen-based input system. When not in use, stylus 1421 resides in acompartment 1413 in the host.

Removable pointer devices according to various embodiments of thepresent invention are particularly applicable to notebook andsubnotebook computers. Such devices are not limited to portablecomputers, however. A removable pointer device as described in theseveral embodiments above may also be implemented in a keyboard usablewith a host computer, such as a desktop or workstation computer,including terminals designed to be used as nodes on a network.

FIG. 28 is an isometric view of a keyboard 1211 having removable pointerdevice 1213 according to an the embodiment of the invention describedabove with reference to FIGS. 21A and 21B. Keyboard 1211 in thisembodiment has a cable 1215 for attaching to a host, and communicatingboth keystroke and pointer data to the host, but may also be implementedwith a keyboard that communicates in another manner with the host, suchas by infrared signals or by inductance coupling.

In various embodiments of keyboards any and all of the embodimentsdescribed above relative to a host notebook-type computer may beimplemented. In the case of a keyboard, it is usual to have a keyboardcontroller for coding keystroke data and imparting the data to the host.In the case of a removable pointer device in a keyboard, the pointermovement data is received by the keyboard controller and coded andpassed to the host along with (multiplexed with) the keystroke data.

It will be apparent to one skilled in the art that there are arelatively large number of changes that may be made in the embodimentsof pointer devices described herein without departing from the spiritand scope of the present invention. Some additions and alternatives havebeen mentioned above. Different embodiments, for example, can berendered in different shapes and sizes, and there are many ways knownfor providing the needed electrical connections and for transmittingsignals.

It will be apparent to one with the skill in the art that there are manychanges that might be made and many other combinations that might bemade without departing from the spirit and scope of the invention. Thereare, for example, many ways to implement the support structure of theμPDA, and to interconnect the active components. One way has beenillustrated by FIG. 2 and described in accompanying text. There are manyalternatives to this preferred structure. There is also a broad range ofsizes and form factors that might be assumed by devices according to thepresent invention. The use of well-known PCMCIA form factors has beendisclosed, but other sizes and forms might also be provided inalternative embodiments. In larger embodiments, on-board peripherals maybe implemented.

In addition to these alternatives, there are various ways theconnectivity of a μPDA bus might be provided. The well-known PCMCIAstandard has been disclosed as a preference, but other connectivity mayalso be used in alternative embodiments. Memory types and sizes mayvary. Means of providing a security code may vary. The nature of theinternal bus may vary. There are many variations that do not depart fromthe spirit and scope of the invention.

What is claimed is:
 1. A digital assistant module having a separatepointer device, comprising:an enclosure; a CPU within the enclosure; amemory coupled to the CPU; a video display coupled to and operable bythe CPU, implemented on a surface of the enclosure; a pair of broadcastantenna within the enclosure adapted to broadcast a carrier waveform ata common frequency but at a known phase difference; a rectifier circuitin the pointer device comprising two antenna connected through a diode;a receiving antenna in the enclosure configured to receive an echo ofthe summed waveforms broadcast by the pair of broadcast antennas; andcircuitry within the enclosure connected to the receiving antenna andadapted for analyzing the received waveform and determining the positionof the pointer from waveform characteristics.
 2. A digital assistantmodule as in claim 1 wherein the pointer device is a stylus with therectifier circuit positioned in a nose region of the stylus.
 3. Adigital assistant module as in claim 2 wherein the stylus is carriedwhen not in use in a compartment within the enclosure.
 4. A digitalassistant module as in claim 1 additionally comprising an expansion businterface comprising an expansion bus connected to the CPU and to afirst portion of an expansion bus connector implemented on a surface ofthe enclosure.
 5. A digital assistant module as in claim 1 additionallycomprising a nonvolatile storage device connected to the CPU andcontaining a code unique to the digital assistant module, for uniquelyidentifying the digital assistant module to connecting digital devices.6. A digital assistant module as in claim 5 wherein the nonvolatilestorage device is an EEPROM device.
 7. A digital assistant system as inclaim 1 further comprising a user-accessible well having electricalconnections for a storage battery for powering functional elements ofthe digital assistant module.
 8. A digital assistant module as in claim1 further comprising a solar energy conversion panel having electricalconnections for attaching to and recharging a storage battery.
 9. Adigital assistant system as in claim 1 wherein the video displaycomprises an LCD display.
 10. A digital assistant system as in claim 1further comprising a host interface bus coupled to the CPU and to afirst portion of a host interface connector at a surface of theenclosure, the host interface bus providing address lines, data lines,and control signal lines, control signals on the control signal linesincluding read/write and at least one memory control signal, but nointerrupt request (IRQ) signal or IRQ signal line.